home *** CD-ROM | disk | FTP | other *** search
- Path: iafrica.com!usenet
- From: cquirke@iafrica.com (Chris Quirke)
- Newsgroups: comp.os.ms-windows.win95.setup,comp.dcom.modems,comp.os.ms-windows.win95.misc
- Subject: Re: Modem hardware conflict? Please help me with this bizarre problem!
- Date: Sat, 09 Mar 1996 18:30:11 GMT
- Organization: Internet Africa
- Message-ID: <4hsppb$qfh@newnews.iafrica.com>
- References: <4gv4al$7u3@matahari.bae.bellcore.com> <4h9orv$aoe@minox.tripnet.se> <4hmh6k$9gu@sinsen.sn.no>
- NNTP-Posting-Host: slipper17133.iafrica.com
- X-Newsreader: Forte Free Agent 1.0.82
-
- leifa@sn.no (Leif Arne Neset) wrote:
-
- >I've been troubled with the same combination of video, 486 and modem/serial
- >port. The problem is that the Diamond stealth card uses some internal
- >registers that have addresses that have the same last bits as the base
- >address of serial port com2. The problem is that the Diamond stealth driver
- >software writes information into registers of the UART of the
- >modem/serial port which then acts funny.
- Does your COM2: use COM4:'s IO port address? AFAIK the SVGA clash
- issue involves COM4:'s IO address, although as COM4: shares IRQ3 with
- COM2:, you may get some spill-over...
-
- >My solution was to strap my ISA serial card/modem as com1 and use
- >the built in VESA combo card com2 for the mouse.
- Me2; the beauty of mouse on COM2: is that you can add an internal
- modem on COM3:, or an external on COM1:, and not have to worry about
- IRQ clashes with the mouse, IO port clashes with S3 or misbehaviour
- due to a "missing" COM3: ;-)
-
-